Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "chore(setup): change defaults for partitions (#6074)" #6086

Merged
merged 1 commit into from
Sep 29, 2022

Conversation

pedro93
Copy link
Collaborator

@pedro93 pedro93 commented Sep 29, 2022

This reverts commit 4cf635e.

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@pedro93 pedro93 requested a review from anshbansal September 29, 2022 09:51
@github-actions github-actions bot added the devops PR or Issue related to DataHub backend & deployment label Sep 29, 2022
@github-actions
Copy link

Unit Test Results (build & test)

584 tests  ±0   580 ✔️ ±0   12m 47s ⏱️ -32s
143 suites ±0       4 💤 ±0 
143 files   ±0       0 ±0 

Results for commit f00e45c. ± Comparison against base commit f83eb6f.

Copy link
Collaborator

@anshbansal anshbansal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@anshbansal anshbansal merged commit 164bc1a into datahub-project:master Sep 29, 2022
@anshbansal anshbansal deleted the revert-shard branch September 29, 2022 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops PR or Issue related to DataHub backend & deployment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants